Skip to content

Conversation

@williambdean
Copy link
Contributor

@williambdean williambdean commented Nov 21, 2025

Description

This adds footer for dates: "Created: | Last updated: "

Screenshot 2025-11-21 at 12 34 28 PM

Is there an appetite for this?

Related Issue

  • Closes #
  • Related to #

Checklist

Type of change

  • New feature / enhancement
  • Bug fix
  • Documentation
  • Maintenance
  • Other (please specify):

@williambdean
Copy link
Contributor Author

williambdean commented Nov 21, 2025

I was considering this repo: https://sphinx-git.readthedocs.io/en/latest/index.html

However, it didn't seem to provide the information that I wanted. However, I don't know the sphinx ecosystem that well. Anyways, this is an implementation.

@williambdean
Copy link
Contributor Author

Anything else needed here?

@ricardoV94
Copy link
Member

@OriolAbril can you take a super fast look?

Copy link
Member

@OriolAbril OriolAbril left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After a very quick look at the results mostly it doesn't seem to be working as intended.

See for example the preview of the "what is pytensor?" notebook:

imatge

It shows both creation and last update date as Oct 23. The notebook was definitely created before that, in fact the watermark a few lines above shows the last rerun date (which I know might not be the last update but might be even more relevant) to be Sep 13. Looking at the source it shows the first and last commit for this particular notebook is Sep 14.

If this works locally it might be an issue with how readthedocs clones the repo which is probably some kind of shallow clone. But given we already have two dates stored in each notebook, in the post directive and the watermark one maybe we could ensure (either with reviews or pre-commit or both) that the date in the post directive is the creation one and the one in the watermark reflects the last update. We can then highlight these two dates with the template being added in this PR

@OriolAbril
Copy link
Member

I am also now realizing the goal of the PR might be to add this for all documentation pages, not only for notebook in which case the workaround wouldn't work and we need to figure out how to get the git approach to work when building on readthedocs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants